Running Setup for an Upgrade
PART 2 OF 6
This topic applies to the Microsoft® Windows Server™ 2003 operating system, Datacenter Edition, and, except where noted, the x64-based and Itanium-based versions of Windows Server 2003, Datacenter Edition.
In This Topic
Preparing Your System for an Upgrade
Product Activation for Products in the Windows Server 2003 Family
This topic provides recommendations for preparing your system before running Setup for Microsoft® Windows Server™ 2003, Datacenter Edition, for an upgrade, and it explains how to run Setup. Before reading this topic or running Setup, be sure to read "Getting Ready for an Upgrade: Windows Server 2003, Datacenter Edition," on your Setup CD. If you have a server cluster, be sure also to read "Upgrading on Cluster Nodes: Windows Server 2003, Datacenter Edition," on your Setup CD.
For more information about the deployment of servers, see the Windows Deployment and Resource Kits Web site at:
For technical information and resources to help you evaluate, deploy, and administer the Windows server operating systems, see the Windows Server TechCenter on the Web at:
| Note: |
|---|
| This release of Windows Server 2003, Datacenter Edition, includes Windows Server 2003 Service Pack 1 (SP1). When you install this release of Windows Server 2003, Datacenter Edition, SP1 is automatically installed at the same time. If you uninstall Windows Server 2003, Datacenter Edition with SP1, SP1 is automatically uninstalled as well. In addition, you cannot uninstall SP1 only. Windows Server 2003, Datacenter Edition for Itanium-based Systems with SP1 is only available on DVD. Windows Server 2003 Service Pack 1 (SP1) for this operating system is available on CD. |
Preparing Your System for an Upgrade
This section describes the basic steps to take in preparing your server for an upgrade.
If you are upgrading Windows Server 2003, Datacenter Edition, on server cluster nodes, be sure to read "Upgrading on Cluster Nodes: Windows Server 2003, Datacenter Edition," on your Setup CD.
Checking the System Log for Errors
Use Event Viewer to review the system log for recent or recurring errors that could cause problems during the upgrade. For information about viewing errors, see Help for the operating system that you are running.
Backing Up Files
Before upgrading, it is recommended that you back up your current files, including anything containing configuration information, for example, the System State and the system and boot partitions. You can back up files to a variety of different media, such as a tape drive or the hard disk of another computer on the network.
Disconnecting UPS Devices
If you have an uninterruptible power supply (UPS) connected to your target computer, disconnect the connecting serial cable before running Setup. Setup automatically attempts to detect devices connected to serial ports, and UPS equipment can cause problems with the detection process.
Starting Setup for an Upgrade
This section explains how to start Setup for an upgrade on an x86-based computer. You can start Setup for an upgrade from the CD or from a network, as described in "Starting an Upgrade" later in this topic.
For important information about upgrades in the context of a domain, see "Getting Ready for an Upgrade: Windows Server 2003, Datacenter Edition," on your Setup CD. For information about unattended Setup and other options available when you start Setup, see "Planning for Unattended Setup" later in this topic.
| Note: |
|---|
| You cannot upgrade from an earlier version of a Windows server operating system to an Itanium-based or x64-based version of a Windows server operating system. |
Providing a Mass Storage Driver or a HAL File
If you have a mass storage controller that requires a driver supplied by the manufacturer, or if you have a custom Hardware Abstraction Layer (HAL) file supplied by the manufacturer, provide the appropriate driver file or HAL file during Setup.
Mass Storage Drivers and the Setup Process
If you have a mass storage controller (such as a SCSI, RAID, or Fibre Channel adapter) for your hard disk, confirm that the controller is designed for products in the Windows Server 2003 family by checking the hardware and software compatibility information in the Windows Catalog at:
If your controller is compatible, but you are aware that the manufacturer has supplied a separate driver file for use with products in the Windows Server 2003 family, obtain the file (on a floppy disk) before you begin Setup. During the early part of Setup, a line at the bottom of the screen prompts you to press F6. Further prompts will guide you in supplying the driver file to Setup so that it can gain access to the mass storage controller.
If you are not sure whether you must obtain a separate driver file from the manufacturer of your mass storage controller, you can try running Setup. If the controller is not supported by the driver files on the Setup CD and therefore requires a driver file that is supplied by the hardware manufacturer, Setup stops and displays a message saying that no disk devices can be found, or it displays an incomplete list of controllers. After you obtain the necessary driver file, restart Setup, and press F6 when you are prompted.
Using a Custom HAL File
If you have a custom Hardware Abstraction Layer (HAL) file supplied by your computer manufacturer, before you begin Setup, locate the floppy disk or other medium containing the file. During the early part of Setup, a line at the bottom of the screen prompts you to press F6: at this time press F5 (not F6). After you press F5, follow the prompts to include your HAL file in the Setup process.
Starting an Upgrade
If you are upgrading to Windows Server 2003, Datacenter Edition, you can start Setup from the CD or from a network. The only operating system from which you can upgrade to Windows Server 2003, Datacenter Edition, is Windows 2000 Datacenter Server.
For information about starting Setup for a new installation, see "Running Setup for a New Installation: Windows Server 2003, Datacenter Edition," on your Setup CD. For information about unattended Setup and other options available when you start Setup, see "Planning for Unattended Setup" later in this topic.
| Important: |
|---|
| To run Setup for an upgrade, you must be a member of the Administrators group on the local computer. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, if you start Setup from a computer running Windows 2000, consider using Run as. Run as is a secondary logon method that you can use to start commands or programs using a different security context. For example, you can log on as a member of the Users group and, without logging off, run a command as a member of the Administrators group. To find more information in Windows 2000 about Run as, on a server running Windows 2000, click Start, click Help, click the Search tab, and then search for runas. |
-
Insert the CD in the drive, and wait for Setup to display a dialog box.
-
Follow the Setup instructions.
-
On a network server, share the installation files by either inserting the CD and sharing the CD-ROM drive or by copying the files from the I386 folder on the CD to a shared folder.
-
On the computer on which you want to install Windows Server 2003, Datacenter Edition, connect to the shared folder or drive that contains the Setup files.
-
Run Setup.exe.
-
Follow the Setup instructions.
Planning for Unattended Setup
This section provides general information about unattended Setup. For detailed instructions on running unattended Setup (also called automated installation), see the Windows Deployment and Resource Kits Web site at:
To simplify the process of setting up a product in the Windows Server 2003 family on multiple computers, you can run Setup unattended. To do this, you create and use an answer file, a customized script that answers the Setup questions automatically. Then, you run Winnt32.exe or Winnt.exe with the appropriate options for unattended Setup. Choose the command according to the operating system that is running when you start unattended Setup:
-
To start unattended Setup on a computer running MS-DOS or Windows 3.x, use Winnt.exe (with the appropriate options).
-
To start unattended Setup on a computer running Windows 95, Windows 98, Windows Millennium Edition, Windows NT®, Windows 2000, Windows XP, or a product in the Windows Server 2003 family, use Winnt32.exe (with the appropriate options). With Windows NT 4.0, before starting unattended Setup, apply Service Pack 5 or later.
To learn about unattended Setup, see the following sources:
-
For detailed instructions on running unattended Setup (also called automated installation): See the Windows Deployment and Resource Kits Web site (described in the first paragraph of this section).
-
To view the command options available for Winnt.exe: On a computer running Windows 3.x or MS-DOS, insert the Setup CD for Windows Server 2003, Datacenter Edition, in the CD-ROM drive and open the command prompt. Then, change to the CD-ROM drive, change to the I386 directory, and type:
winnt /?
-
To use an x86-based or x64-based computer to view the command options available for Winnt32.exe: On a computer running Windows 95, Windows 98, Windows Millennium Edition, Windows NT, Windows 2000, Windows XP, or a product in the Windows Server 2003 family, insert the Setup CD for Windows Server 2003, Standard Edition, in the CD-ROM drive, and open the command prompt. Then, change to the CD-ROM drive, change to the I386 directory, and type:
winnt32 /?
-
To use an Itanium-based computer to view the command options available for Winnt32.exe: On an Itanium-based computer running Windows XP 64-Bit Edition; the Itanium-based version of Windows Server 2003, Enterprise Edition; or the Itanium-based version of Windows Server 2003, Datacenter Edition, insert the Setup CD for the product in the CD-ROM drive and open the command prompt (click Start, click Run, and then type cmd). Then, change to the CD-ROM drive, change to the IA64 directory, and type:
winnt32 /?
Product Activation for Products in the Windows Server 2003 Family
After you install a product in the Windows Server 2003 family, if the product was purchased individually rather than through a volume licensing arrangement, you will have to activate the product unless your hardware manufacturer has preactivated it for you. Product activation is quick, simple, and unobtrusive, and it protects your privacy. It is designed to reduce software piracy (illegal copies of a product). Over time, reduced piracy means that the software industry can invest more in product development, quality, and support. This results in better products and more innovation for customers.
The following details help explain product activation:
Software reminders Until you activate your product, it provides a reminder each time you log on and at common intervals until the end of the activation grace period stated in your End-User License Agreement (30 days is the typical grace period). If your activation grace period passes and you do not activate the product, your computer will continue to function, except that when you log on locally or log on through Remote Desktop for Administration (the new name for the Windows 2000 functionality known as Terminal Services in Remote Administration Mode), you will only be able to use the Activate Windows Wizard.
How the software handles activation Activation is simple and anonymous. When you activate your product, it means that your product key is now associated with the computer (the hardware) it is installed on. After that happens, your product key cannot be used for activation on other computers (unless you are enrolled in a special program that permits additional activations, for example, a program through the Microsoft Developer Network).
Your local operating system does some of the work for creating the association between your product key and the computer it is installed on. It uses your Product ID, which is derived from your product key, and puts it together with a coded number (called a hardware hash) that uniquely represents the hardware components that make up your computer (without representing any personal information or anything about the software). When you activate, you provide this number, through the Internet or by phone, so that it can be confirmed as representing a legal installation. After you activate, if another person has an illegal copy of your software, and that person tries to use your product key to activate the software on another computer, the coded numbers will show that your product key is already associated with a particular set of hardware (your computer). The other person’s activation will not work.
The Installation ID that the local operating system generates, representing the association between your product key and the computer it is installed on, is used only for the purpose of activation.
Methods for activation After your operating system is installed, begin activation by clicking Start and then clicking Activate Windows (you can also click the key icon that appears in the lower right corner of the screen). By following the instructions on the screen, you can activate through the Internet or by phone:
-
Internet: When you activate through the Internet, your computer transmits coded information that shows that your product key is associated with your computer hardware. Activation is carried out through a secure server. A confirmation ID is passed back to your computer, automatically activating your product. This process normally takes just a few seconds to complete. No personally identifiable information is required to activate your product.
-
Phone: When you activate by phone, information on the screen guides you through a few simple steps. When you choose the country where you are located, a phone number (toll-free, wherever possible) appears on your screen. When you call the number, a customer service representative asks for the Installation ID that is displayed on your screen. The customer service representative enters that number into a secure database, confirms that the number represents a legally installed product, and provides a confirmation ID to you. Then, you type the confirmation ID into the spaces provided on the screen, and activation is complete.
Reactivation (rarely needed) If you overhaul your computer by replacing a substantial number of hardware components (not just a few), the operating system might view your hardware as a completely different computer, not the one on which you activated. In this situation, you can call the telephone number displayed on the telephone activation screen, and, through a quick, simple process, you can reactivate your product.
Product Activation Compared to Product Registration
Product activation is not the same as product registration. As discussed above, product activation is required, and it is completely anonymous. Product registration, in contrast, is completely optional, and it allows you to provide personal information, such as your e-mail address, if you choose. Registration entitles you to receive information about product updates and special offers directly from Microsoft. All registration information provided is stored securely, and no information is ever loaned or sold to other parties.